-
Notifications
You must be signed in to change notification settings - Fork 813
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generate release notes and Changelog using Github #3022
Generate release notes and Changelog using Github #3022
Conversation
Build Failed 😱 Build Id: 6ed906c3-06ea-4715-9c3a-3dc14f62de5e To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
Let's add the changes we expect to see in the release notes too please. |
Build Failed 😱 Build Id: d04b8938-0fe2-4b50-8ba3-fb749d12b16b To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
Build Succeeded 👏 Build Id: ff7ec30a-0584-4c2b-b338-cc6449cd8ddd The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
Build Succeeded 👏 Build Id: a8187865-45b2-466d-9b0e-91bcbd72e9fe The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great! Nice changes overall on the release checklist (as an aside, if you ever want to make improvements, please feel free to do so).
Just some minor things, and I think this will be good for the next release 👍🏻
.github/release.yml
Outdated
changelog: | ||
exclude: | ||
labels: | ||
- area/meta |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- area/meta |
So I realised something - our release docs are wrong, we don't ignore area/meta
at all!
.github/release.yml
Outdated
- question | ||
- invalid | ||
- wontfix | ||
- priority/wontfix |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- priority/wontfix |
I don't think we have this label anywhere?
.github/release.yml
Outdated
- wontfix | ||
- priority/wontfix | ||
categories: | ||
- title: Breaking Changes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- title: Breaking Changes | |
- title: Breaking changes |
Just for capitalisation consistency.
.github/release.yml
Outdated
- title: Fixed bugs | ||
labels: | ||
- kind/bug | ||
- title: Security |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- title: Security | |
- title: Security fixes |
@@ -23,7 +23,7 @@ and copy it into a release issue. Fill in relevant values, found inside {} | |||
|
|||
- [ ] Run `make shell` and run `gcloud config configurations activate agones-images`. | |||
- [ ] Review [closed issues with no milestone](https://github.com/googleforgames/agones/issues?q=is%3Aissue+is%3Aclosed+no%3Amilestone++-label%3Ainvalid+-label%3Aduplicate+-label%3Aquestion+-label%3Awontfix++-label%3Aarea%2Fmeta) and add relevant ones to the current milestone. | |||
- Issues tagged as `invalid`, `duplicate`, `question`, `wontfix`, or `area/meta` can be ignored | |||
- Issues tagged as `invalid`, `duplicate`, `question`, `wontfix`, or `area/meta` can be ignored |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Issues tagged as `invalid`, `duplicate`, `question`, `wontfix`, or `area/meta` can be ignored | |
- Issues tagged as `invalid`, `duplicate`, `question`, `wontfix`, or `area/meta` don't need review. |
I see the confusion in this step - suggestion less ambiguous language. WDYT?
- [ ] Move the CHANGELOG.md to the root of this repository, replacing any previous versions. | ||
- [ ] Ensure the [helm `tag` value][values] is correct (should be {version}) | ||
- [ ] Ensure the [helm `Chart` version values][chart] are correct (should be {version}) | ||
-For example, if you are creating the {version} release, then you would deploy the {version}-1 service (release minus one, and then replace dots with dashes) [check for this change in GCP -> App Engine/Service] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
-For example, if you are creating the {version} release, then you would deploy the {version}-1 service (release minus one, and then replace dots with dashes) [check for this change in GCP -> App Engine/Service] | |
- For example, if you are creating the {version} release, then this would deploy the {version}-1 service (release minus one, and then replace dots with dashes) [check for this change in GCP -> App Engine/Service] |
Also was the part in (release minus one, and then replace dots with dashes) [check for this change in GCP -> App Engine/Service]
meant to be a markdown link?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It isn't a link, just to confirm the successful deployment in the app engine/ service. Added almost all the steps from the release video here😀
- [ ] Change to the `sdks/nodejs` directory and run the command `npm version {version}+1-dev` to update the package version | ||
- [ ] Move the [`sdks/csharp/sdk/AgonesSDK.nuspec` and `sdks/csharp/sdk/csharp-sdk.csproj`][csharp] to {version}+1-dev | ||
- [ ] Update the [`sdks/unity/package.json`][unity] package file's `Version` field to {version}+1-dev | ||
- [ ] Update the [`sdks/unity/package.json`][unity] package file's `version` field to {version}+1-dev |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since we're fixing things, can we add a link to [unity]
down below, so we finally don't have a broken markdown link 😄
Build Succeeded 👏 Build Id: 4a3cdffb-7987-4d9f-a66a-a0648e5bf7bf The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Kalaiselvi84, markmandel The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
New changes are detected. LGTM label has been removed. |
Build Succeeded 👏 Build Id: 6ba72262-4e06-484e-b186-06fe161a6883 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
* Generate release notes using Github * Apache header included * update in release checklist * del a extra space * fmt file * few changes in the checklist * Changes in release files
What type of PR is this?
/kind cleanup
What this PR does / Why we need it:
Which issue(s) this PR fixes:
b/271147150
Special notes for your reviewer: